This page last changed on Dec 14, 2004 by plightbo.

Key Changes

  • JavaScript client validation support - not totally complete, but basic validators work well. Look at the validators.xml file include in src/example to see how you can configure your validators to do client side validation on top of their normal duties
  • The label attribute in UI tags are no longer required
  • The themes and templates in UI tags behave like they did in 1.x
  • A new theme, in addition to the existing "xhtml" one, called "simple" is included that doesn't have any of the labels, error reporting, or table rows that the "xhtml" template has. This is more in line with the tags included with Struts.
  • New UI tags for CSS styles and classes added: cssStyle and cssClass
  • Old action!command URL support works again. This means you can invoke a doCommand() method like in 1.x
  • ww:param tag no longer requires the name attribute (for ordered params, like with ww:text). It also evaluates the the body as the value if no value is given.
  • UI tags now have access to the FormTag parameter map using the "form" key. This means $parameters.form.name would return the form name, for example. The result is that complex JavaScript-based components can be built.

Migration Notes

Version Description Old Code New Code
2.0 WebWorkUtil has been refactored into a number of classes, and the constructor has changed. If you were using it for Velocity support before, look at VelocityWebWorkUtil now
2.0 The webwork.ui.templateDir configuration property has been broken into webwork.ui.templateDir and webwork.ui.theme
webwork.ui.templateDir= /webwork/mytheme
webwork.ui.templateDir = /webwork 
webwork.ui.theme = mytheme
2.0 "namespace" attribute of the ww:action tag is now evaluated; those upgrading from 2.0 will need to place single quotes around the attribute value <ww:action namespace="/foo" .../> <ww:action namespace="'/foo'" .../>
2.0, but not 1.x theme and template attributes in UI tags have changed are now evaluated; those upgrading from 2.0 will need to place single quotes around the attribute value <ww:xxxx theme="/template/foo" template="bar.vm"/> <ww:xxxx theme="'foo'" template="'bar.vm'"/>
1.x, 2.0 label UI tag evaluates the value attribute now instead of the name attribute <ww:label name="'Foo'"/> <ww:label value="'Foo'"/>

Changelog

OpenSymphony JIRA (25 issues)
T Key Summary
Improvement WW-592 Upgrade commons-logging
Bug WW-560 SessionMap holds on to requests when it doens't need to
New Feature WW-546 Make the config-browser show validators applied via the XML validation files
Bug WW-544 Velocity result hardcodes contenttype and encoding
Improvement WW-541 Webpage link for download
Bug WW-537 Velocity tag outputs to the response, not the velocity writer
Bug WW-530 Config Browser doesn't work after lates ActionConfig refactoring
Bug WW-519 ActionTag should evaluate namespace attribute
Improvement WW-518 Label attribute shouldn't be required
Bug WW-517 Themes and templates should behave like 1.x
Improvement WW-516 Simple theme that has no tables and xhtml extends from
Bug WW-515 Class attribute is illegal
Bug WW-514 Form tag double evaluates name attribute
Bug WW-503 Fix tag libraries
Bug WW-502 foo!default.action should work
New Feature WW-501 JavaSript-based client side validation
Bug WW-500 ww:param tag fixes
New Feature WW-499 UI tags should have access to form
Task WW-488 Check QuickStart Guide to make sure it works
Bug WW-487 WebWorkConversionErrorInterceptorTest in wrong branch
Bug WW-484 label tag problems
Bug WW-478 URLTag tld entry does not correspond with actual property
Improvement WW-476 WebWork needs a simple changelog for each release
Bug WW-475 Multipart encoding still not fixed
Bug WW-474 Ability to dynamically create array of Objects from a given request

Document generated by Confluence on Dec 14, 2004 16:36